Automation in Digital Preservation Editor Final Reports of the Break­out Sessions Session 1: Preservation Ready Systems – Digital Preservation and Enterprise Architecture

(discussion facilitator and rapporteur Jose Borbinha) The Problem A system is a collection of components organized to accomplish a specific function or set of functions [1]. In each moment the systems’ functions are perceived as outputs resulting from the combination of the state of its information model, of its inputs, and of the behavioural model defined for that system. We can classify the systems’ inputs and outputs as, in general, matter, energy or information. Information Systems are those conceived and created considering that our inputs, processes and outputs will deal with information. Since these systems are increasingly relevant in our actual technological paradigm, we recognize it is important to include in the core concern of Digital Preservation (DP) the scope of Information Systems. For that we need to bring to discussion two important concepts:  Non‐Functional Requirement: In Systems Engineering and Requirements Engineering, a Non‐Functional Requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. This should be contrasted with Functional Requirements that define specific behaviour or functions [5]. A Functional Requirement defines what a system is supposed to do whereas a Non‐Functional Requirement defines how a system is supposed to be. Non‐Functional Requirements are often called qualities of a system, which sometimes are also called "constraints", "quality attributes", "quality goals", "quality of service requirements" and "non‐behavioral requirements“ [5].  System Architecture: In Software Engineering the architecture of a system is defined as “the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution”